-
Notifications
You must be signed in to change notification settings - Fork 130
WIP:Documentation/citation style #371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
What citation style is this? |
doc/commenting.rst
Outdated
| - For more than 3 authors, place "et al." after the third one | ||
| - For more than 1 editor, place "et al." after the first one | ||
| - Naming pages at the end is optional, to ease finding in long texts or for direct citations | ||
| - Scheme is as follows (replace tags with corresponding values): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree
It is similiar to APA, but not identical. Here, the is at the end, whereas APA defines the in () after the author. We can go for APA completely to have something standardized. In the meantime, I continue and try out italic in document title of the reference, so there will be some slight changes. |
|
Complete apa is good. |
|
So we will go for full APA style. |
|
I have pushed the citation style section in the doc. |
|
@jdsika @PhRosenberger Just as side note for checking the sphinx rst syntax I use this site. |
vkresch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PhRosenberger Thank you for the standardization according to DIN overall looks really good. I only found really minor issues and small questions.
doc/commenting.rst
Outdated
| **Citation style for different sources:** | ||
|
|
||
| - Within the text, the number system is used with the number of the source in brackets [#] for mentioning. | ||
| - We use the so called "APA style"`link <https://apastyle.apa.org/>`_ from the American Psychological Association for referencing (). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change the link into "APA style <https://apastyle.apa.org/>_" and remove the brackets at the end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the support, will be changed.
doc/commenting.rst
Outdated
| - In the references list, the number in brackets [#] is followed by a full citation. | ||
| - For writing the title in italic, use <em>title</em> | ||
| - Author names are written as <surname>, <initial(s)> like Authorname, A. A. | ||
| - Editor names are written as <initial(s)> <surname> like B. B. Editorname |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Minor issue) Decide on consistent period usage for bullet points.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
osi_environment.proto
Outdated
| // | ||
| // \par References: | ||
| // - [2] SHEPARD, Frank D. Reduced visibility due to fog on the highway. | ||
| // - [2] SHEPARD, Frank D. <em>Reduced visibility due to fog on the highway.</em> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the bullet point here be removed too like in the example in comment.rst?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not done with the .proto files, so yes, I will remove the bullet points.
osi_environment.proto
Outdated
| // - [2] SHEPARD, Frank D. Reduced visibility due to fog on the highway. | ||
| // - [2] SHEPARD, Frank D. <em>Reduced visibility due to fog on the highway.</em> | ||
| // Transportation Research Board, 1996. | ||
| // - [3] [StVO 17 chapter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here, too? (bullet point removal)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
PhRosenberger
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdsika @PhRosenberger Just as side note for checking the sphinx rst syntax I use this site.
I use CLion as IDE, which has y build in interpreter, which is very comfy:-)
doc/commenting.rst
Outdated
| // | ||
| // \par Reference: | ||
| // [1] Rapp, C.: Grundlagen der Physik, in: Hydraulik für Ingenieure und Naturwissenschaftler, Springer Vieweg, Wiesbaden, 2017, p. 105 | ||
| // [1] Rapp, C. (2017). Grundlagen der Physik. <em>In Hydraulik für Ingenieure und Naturwissenschaftler</em> (pp.23-36). Springer Vieweg. Wiesbaden, Germany. https://doi.org/10.1007/978-3-658-18619-7_3. p. 105. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
So, I am done with the existing citations. For adding new citations, where they are missing, I would propose to create a new branch. Actually, it took a lot of time to find a good citation style and especially for correcting the existing ones, so finding missing citations will take probably even more time. A possible work-around could be to wait for ISO23150 to be publicly available and cite this then. What do you think, @jdsika, @vkresch, and others? |
|
Actually, the line breaking with " \n " from the last commit fails because of the non-ASCII testing. |
|
@PhRosenberger it's mostly because of the character "ß" in "Straßenverkehrs-Ordnung" and "ü" in "für". So basically we need to decide if we want to cite only in english or only in german. If we decide on german then we need to remove the non-ascii test. This could cause some bugs/erros in the doxygen generation since this is the reason behind the test. This should be tested accordingly. |
|
I would go for an "english only" style |
Does this mean only English sources? I prefer to change writing into "ss", "ue", "ae", and "oe". |
|
Ready for merge into master now. |
|
I am fine with ö as oe! |
vkresch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I'm not sure if the line length influences the doxygen ouput. Normally it shouldn't.
|
@PhRosenberger thank you very much - good job! |
Reference to a related issue in the repository
Related to #356
Add a description
This is my proposal for a citation style. Please check before I change all existing citations and add missing ones.
Mention a member
@jdsika could you do the check?
Check the checklist